This guide is for people coming from the previous version of Playlab. It will be retired in August 2026 once everyone has migrated. For current Playlab guidance, see Learn on Your Own or Feature Documentation.
What stays the same
Migration preserves what was already working.- Your apps move with the same prompts, references, model selection, and starter inputs
- App owners are preserved
- Workspaces keep their names, members, and apps
- Voice and dictation carry over
- Conversation history is retained and queryable
- References at the org, workspace, and app level all carry over
- Integrations (SSO, rostering) keep working
- Activity history stays in place
- Old URLs continue to redirect to the current paths, so bookmarks, LMS embeds, and class materials keep resolving
What changed
The structure of how content lives changed. The content itself did not.
For the full mapping, see the workflow cheat sheet.
What you can do now (couldn’t before)
Six capabilities are new. Each one solves a problem partners ran into often. Here’s the shape of the change at a glance:
Editor sharing on a single app. Add a peer as Editor on one app and they can edit that app only. They don’t get access to your other apps or your workspace. Previously, the only way to grant edit access was through workspace membership, which over-shared. See Collaborating on an app.
One app in many classes (no remixing). Add the same app to as many workspaces as you need. The app keeps a single owner. Activity stays segmented per class. When the owner publishes a new version, every class using the app sees the update. Previously, this required remixing the app per class and copies drifted. See Using an app across multiple classes.
Direct sharing with another organization. From the Share modal, type the destination organization, set permissions, send. Cross-org sharing is a first-class flow. Previously, the only path was remixing into the recipient org. See Sharing with groups and orgs.
Collections for curated bundles. Build a Collection of apps once, share it with a partner organization, and that organization gets the whole bundle. Updates propagate. Previously, this required remixing each app into each district’s workspace. See Share with Collections.
Centralized flag review. All flagged messages from across an organization surface in one dashboard. Filter by workspace, severity, member, or date. Previously, finding flags meant walking every workspace. See Centralized org monitoring.
Workspace building permissions. Three toggles per workspace: members can build apps, members can see each other, members can share beyond the workspace. Set them to match the class. Previously, workspaces had one shared mode (everyone builds or no one does). See Workspace building permissions.
Privacy as a default change
Now, every new app starts private. You and your org’s admins can see it. Nobody else, until you share or publish. Previously, an app you created was visible to everyone in the workspace from day one. The default flipped.
Where to next
Walk me through migration
What to do before, during, and after the migration window.
Show me the workflows side-by-side
Every common workflow with before-and-after columns.
FAQ
Will my class links from last year still work?
Will my class links from last year still work?
Yes. Old URLs redirect to the current paths. Bookmarks, LMS embeds, and class materials should keep resolving.
Do I have to learn the new version before my org migrates?
Do I have to learn the new version before my org migrates?
No. The basics work the same. The new capabilities (Collections, cross-workspace, centralized monitoring) become available after migration. Read at your own pace.
Where do I get help during my org's migration?
Where do I get help during my org's migration?
The Playlab team is the first stop. Email [email protected], or drop into Office Hours for real-time questions.
Last updated: 06-17-2026 Contact us at [email protected]